chore(test): enforce Vitest coverage thresholds in CI#797
Conversation
|
@Olasunkanmi975 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
Hi maintainer, please review this pr |
|
Great job so far There’s just one blocker — the workflow is failing. Could you take a look and fix it so all checks pass? Happy to review again once that’s done. |
|
Workflow is still failing |
|
@RUKAYAT-CODER2025 please review there is nothing to fix there all good |
|
Workflow is still failing |
Olasunkanmi975
force-pushed
the
chore/coverage-threshold-enforcement
branch
from
b9a48c7 to
c95bc76
Compare
|
@RUKAYAT-CODER Hi maintainer please review this pr and merge, all resolved |
|
@RUKAYAT-CODER Hi maintainer please review this pr and merge, all resolved |
|
Thank you for contributing to the project. |
2 participants
##closed #751
Summary
Adds automated coverage enforcement to the test pipeline by configuring minimum Vitest coverage thresholds, integrating coverage reporting into CI, and documenting the project's coverage policy.
Changes
Configured Vitest to use the V8 coverage provider with minimum thresholds:
Updated the CI workflow to run coverage with JSON and LCOV reporters.
Added LCOV upload for coverage trend tracking (using the repository's configured coverage service).
Documented the coverage policy and local coverage workflow in
CONTRIBUTING.md.Testing
Verified:
Validation
npm test npm run test:coverage npm run lintNotes
This change introduces coverage enforcement only. It does not modify application behavior or existing test logic.